Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1753

reference
488-tree-1
name
1753
tree-preservation-order

undefined

488-tpo-1
uprn
address-text
point
POINT (-1.022621 50.884823)
geometry
MULTIPOLYGON (((-1.022536 50.884814,-1.022540 50.884831,-1.022552 50.884846,-1.022570 50.884858,-1.022594 50.884866,-1.022620 50.884869,-1.022647 50.884867,-1.022671 50.884859,-1.022690 50.884847,-1.022702 50.884833,-1.022707 50.884816,-1.022703 50.884799,-1.022691 50.884784,-1.022672 50.884772,-1.022649 50.884764,-1.022622 50.884761,-1.022596 50.884764,-1.022572 50.884771,-1.022553 50.884783,-1.022541 50.884798,-1.022536 50.884814)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL